Method and system for the automated collection and display of database information via a communications network

ABSTRACT

A method and system for gathering end-user data over a network infrastructure using input pages generated from Requestor specifications and for outputting end-user data based on output generated from Requestor specifications by using a common identifier to maintain associations with the required data information and the Requestor input and output specifications.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not Applicable

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

REFERENCE TO SEQUENCE LISTING, A TABLE, OR A COMPUTER PROGRAM LISTINGCOMPACT DISK APPENDIX

Not Applicable

BACKGROUND OF THE INVENTION

The present invention relates to a computer method and system forgathering and displaying information, particularly to a method andsystem for gathering and displaying information over the Internet.

The Internet and the World Wide Web (the “web”) in particular hasexperienced tremendous growth in the past several years. The web serviceallows a server system to send graphical web pages of information to aremote client system. Web documents are typically defined using HyperText Markup Language (“HTML”), a computer language which provides astandard set of tags that define how a web page is to be displayed. Eachweb resource is uniquely identifiable by a Uniform Resource Locator(“URL”). To view a specific web page, a client computer system specifiesthe URL for that web page in a request sent to the server system.On-line tools exist which permit the creation of an informational webpage or group of web pages with little or no programming know-how. Theweb-site created using these resources becomes instantly available andaccessible world-wide using a client system.

Special purpose web-site creation tools such as those for creatingcatalogs exist to facilitate the collection of specific information suchas orders (e.g. http://www.createastore.com). These are adequate ifinformational requirements fit a particular model (e.g. the purchasingmodel) and if data needs don't change frequently. However, it is stillvery difficult to gather and display customized elements of informationwhich do not fit a particular model. To collect such customized elementsof information typically necessitates enlisting the aid of a specialistsuch as a programmer to create a customized database-enabled web-site ordatabase access application.

These database access applications have recently gained popularity onthe web. These systems essentially require three additional components:(1) a database for the storage and retrieval of user-entered data, (2)input pages for the collection of data to populate the database, and (3)output pages for the display of the entered data. Each component must becreated and the associations between each must be maintained and keptcurrent. Typically the components are manually created and theassociations between the database, input pages and output pages areestablished at the time of creation of the system. Where datarequirements subsequently change, however, the database and associatedinput and output pages which depend upon the database are manuallyupdated. This manual revision process is not immediate and not conduciveto frequent changes. Moreover, keeping database associations with theinput and output pages is especially difficult where subsequent changesare made by another person since the creation of the database, inputpages, and output pages may not have been standardized. This isespecially problematic in situations where data requirements changequickly and/or frequently.

There are tools that can assist in this process but these typicallynecessitate using additional off-line development tools and thus theresults again are not immediate. As well, these development tools oftenrequire specialized programming skill, additional hardware or additionalsoftware. On-line tools exist to provide discrete packages to deal withparts of the problem. For instance, form generation tools (e.g.http://www.createforms.com) may deal with the input page aspect but donot deal with the output page or database association aspects. Moreover,such a piece-meal approach does not result in an integrated andcoordinated solution.

Thus the process of gathering and displaying end-user data containingcustomized elements of data is inconvenient and unsatisfactory. What isneeded then is a system that overcomes the foregoing disadvantages.

BRIEF SUMMARY OF THE INVENTION

The present invention, generally speaking, uses a computer network and adatabase to provide a dynamic information system in which theinformation content and the display of the information content is basedon requirements entirely user-specified and associated with a requesteridentifier. Requests are received from individual users of the computernetwork, Requestors, to electronically gather information. Input andoutput specification requirements are received from the Requestor andstored in dynamic format with an associated identifier and requestoridentifier. Entries from individual users, end-users, containing theinformation to be electronically stored are sent along with therequestor identifier and input identifier and validated using theassociated specifications and if valid are automatically collected andstored in the database in searchable and retrievable form. Entries aremade accessible on the computer network when valid requestor identifierand output identifier are received from an end-user along with therequest. In response to end-user requests, the database is searched andentries are retrieved based on dynamic search specifications and displayspecifications of the associated requestor identifer and outputidentifier. Entries are served to end-users in a hardware-independentpage description language.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an embodiment of the presentinvention;

FIG. 2A through FIG. 2T are screen displays showing use of the systemand method of the present invention;

FIG. 3A is a flow diagram of a routine used by an end-user to generate aweb page search result in which a requestor identifier and an outputidentifier is sent to the server system;

FIG. 3B is a flow diagram of a routine used by an end-user to input userdata in which a requestor identifier and an input identifier is sent tothe server system;

FIG. 4A is a flow diagram of a routine used by a Requestor to add inputpage specifications in which a requester identifier and an inputidentifier is sent to the server system;

FIG. 4B is a flow diagram of a routine used by a Requestor to update aninput page specification in which a requester identifier and an inputidentifier is sent to the server system;

FIG. 4C is a flow diagram of a routine used by a Requestor to add anoutput page specification in which a requestor identifier and an outputidentifier is sent to the server system; and

FIG. 4D is a flow diagram of a routine used by a Requestor to update anoutput page specification in which a requester identifier and an outputidentifier is sent to the server system.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a block diagram illustrating an embodiment of the presentinvention. The server system 110 includes a server engine 111, arequestor identifier/requestor table 112, a requestor identifier/inputidentifier table 113, a requestor identifier/output identifier table114, a requester information database 115, a requestor inputspecifications database 116, a requestor output specifications database117, and an end-user input database 118.

The server engine receives requests to access web pages identified byURL and provides the web pages to the various client systems. Each suchrequest includes an accompanying requestor identifier along with eitheran input or an output identifier to effect a database interactionfunction.

The requester information database 115 contains requester informationfor various requestors. The requestor information includes user-specificinformation such as name information, address information, and otherauthentication information.

The input specifications database 116 contains input specificationsinformation. Input specifications information includes database fieldinformation and field validation information which aid in defining whatinformation will be accepted from the end-user by defining the databasestructure and acceptable input values.

The output specifications database 117 contains output specificationsinformation. Output specifications information includes database fieldinformation and field display information which aid in defining whatinformation will be displayed and how it will be displayed to anend-user.

The end-user input database 118 contains end-user entered information.End-user entered information includes information which has been enteredby a user and which has been validated and found to comply with theassociated input specifications information in the input specificationsdatabase 116.

The requester identifier/requestor information table 112 contains amapping from each globally unique requestor identifier that identifiesrequestor information associated with the requestor identifier.

The requestor identifier/input table 113 contains a mapping from eachrequestor identifier-input identifier combination to the associatedinput specifications information in the input specifications database116.

The requestor identifier/output table 114 contains a mapping from eachunique requestor identifier-output identifier combination to theassociated output specifications information in the outputspecifications database 117.

The client system 120 contains a browser and an assigned requestoridentifier. In one embodiment, the server system assigns and sends therequestor identifier to the client system once when the client systemfirst interacts with the server system. From then on, the client systemincludes its requestor identifier with all messages sent to the serversystem so that the server system can identify the source of the message.

In an alternate embodiment, the requestor identifier is assigned afteruser authentication such as after the provision of a valid password oruser sign-up information. The client system in 120 can also contain aninput identifier or an output identifier depending on the options theclient system selects. In one embodiment, the server system assigns aninput identifier once valid input specifications information along withan authenticated requester identifier has been submitted to the serversystem. In another embodiment, the server system assigns an outputidentifier once valid output specifications information along with anauthenticated requestor identifier has been submitted to the serversystem.

The client system 130 contains a browser which is used to make pagerequests to the server system. Each request made to the server system isaccompanied by a requester identifier and either an input identifier oroutput identifier depending on the desired function the client systemwishes to perform.

The server system and client systems interact by exchanging informationvia a communications network link 140, which may include the Internet.One skilled in the art would appreciate that the system can be used invarious environments other than the Internet. Various communicationchannels may be used such as local area network, wide area network, orpoint-to-point dial up connection. Also, a server system may compriseany combination of hardware or software that can accept and userequestor identifier and input or output identifiers in the manipulationof data in response to receipt of a client system page requestaccompanied by the requester identifier and input or output identifiers.A client system may comprise any combination of hardware or softwarethat can interact with the server system. These systems may includetelevision-based systems, touch-screen system or various other consumerproducts through which a requester identifier and an input identifier oroutput identifier may be passed.

In order to convey the manner in which the automated gathering anddisplay of information is used, screen displays of the graphical userinterface will now be described.

When a requester wishing to gather and display customized informationfirst visits the site, he or she is presented with an authenticationscreen for login or sign-up like FIG. 2A. After authentication, theclient system is assigned a requestor identifier and presented with aselection page FIG. 2B.

If Add Input Specifications is chosen, the user is presented with aselection page FIG. 2C listing previously entered input pages and anoption to create a new input page. If the user chooses to create a newinput page, the requestor identifier is sent to the server system alongwith the request to create a new input page and the server systemassigns a new input identifier and sends the identifier to the clientsystem. If the user chooses to add a new input specification to anexisting input page, the user selects the relevant page and the inputidentifier is set at the client system.

The user is then presented with a web page, FIG. 2D, showing inputspecifications information that may be entered for the chosen inputidentifier. This example web page contains a field type input section201 containing one or more selection boxes to indicate the databasefield options corresponding to the various database field optionsavailable for a new input field, a display details section 202, and avalidation details section 203. One skilled in the art would appreciatedthat these sections can be rearranged, adapted or omitted in variousways. When the user enters the information in the fields and selectsSubmit, the information is sent along with the requestor identifier andthe input identifier. The server system returns a confirming web pageFIG. 2E.

If Update Input Specifications is chosen, the user is presented with aselection page FIG. 2F listing previously entered input pages. The userselects the relevant input page and the input identifier is set at theclient system. The user is then presented with a web page, FIG. 2G,showing input specifications records for the chosen input page. The userselects the relevant input specifications record and the input recordidentifier is set at the client system. The user is then presented witha web page, FIG. 2H, showing input specifications information that havepreviously been entered. When the user edits the entry to his or hersatisfaction and selects Submit, the information is sent along with therequestor identifier, input identifier and input record identifier. Theuser is then presented with a confirming web page FIG. 2I.

If Add Output Specifications is chosen, the user is presented with aselection page FIG. 2J listing previously entered output pages and anoption to create a new output page. If the user chooses to create a newoutput page, the requestor identifier is sent to the server system alongwith the request to create a new output page and the server systemassigns a new output identifier and sends the identifier to the clientsystem. If the user chooses to add a new output specification to anexisting output page, the user selects the relevant page and the outputidentifier is set at the client system.

The user is then presented with a web page, FIG. 2K, showing outputspecifications information that may be entered for the chosen outputidentifier. This example web page contains a field selection section 204containing a listing of fields that may be displayed on the output webpage and a display details section 205 containing various displayoptions. In one embodiment the listing in the field selection section204 is derived from the database fields previously defined in the inputspecifications database 116 for that requestor identifier. One skilledin the art would appreciated that these sections can be rearranged,adapted or omitted in various ways. When the user enters the fieldinformation and selects Submit, the information is sent along with therequestor identifier and the output identifier. The server systemreturns a confirming web page FIG. 2L.

If Update Output Specifications is chosen, the user is presented with aselection page FIG. 2M listing previously entered output pages. The userselects the relevant output page and the output identifier is set at theclient system. The user is then presented with a web page, FIG. 2N,showing output specifications records for the chosen output page. Theuser selects the relevant output specifications record and the outputrecord identifier is set at the client system. The user is thenpresented with a web page, FIG. 2O, showing output specificationsinformation that have previously been entered. When the user edits theentry to his or her satisfaction and selects Submit, the information issent along with the requestor identifier, output identifier and outputrecord identifier. The user is then presented with a confirming web pageFIG. 2P.

When an end-user interacts with the system, he or she must provide arequestor identifier for each request.

To obtain a search result display, the client uses a web page such asFIG. 2Q to send end-user search information along with the requestoridentifier and output identifier to the server system. For instance,FIG. 2Q shows an entry to view all members who have signed-up for a golftournament and who have a skill level value of 4. The requestoridentifier and output identifier can be included in the UniversalResource Locator and a URL for a request might behttp://www.centranet.com/outputinfo.html?rid=xxx&oid=zzz, where xxxrepresents a requester identifier and zzz represents an outputidentifier. After the user enters the end-user search information andselects Submit, the information is sent along with the requesteridentifier and output identifier. The flow described in FIG. 3A below isexecuted. The user is then presented with a web page FIG. 2R showing theresults of the request. FIG. 2R is an example of the results of theoutput specifications in FIG. 4C and FIG. 4D.

To enter end-user data, the client uses a web page FIG. 2S to send userinput information including the requestor identifier and inputidentifier to the server system. For instance, FIG. 2S shows an entry toenter sign-up information into a golf tournament sign-up page where theuser enters name, e-mail and skill level information. A URL for arequest might behttp://www.centranet.com/inputinfo.html?rid=xxx&iid=yyy, where xxxrepresents a requestor identifier and yyy represents an inputidentifier. FIG. 2S is an example of the results of the inputspecifications in FIG. 4A and FIG. 4B. After the user enters theinformation and selects Submit, the information is sent along with therequestor identifier and input identifier. The flow described in FIG. 3Bbelow is executed. The user is then presented with a web page FIG. 2Tconfirming the input request.

One skilled in the art would appreciate that the web pages in FIG. 2Qand FIG. 2S can be generated by the server system or generatedexternally.

FIG. 3A is a flow diagram of a routine to generate a web page searchresult in which a requester identifier and an output identifier is sentto the server system.

Each time end-user search information is sent in step 301 from an entrypage such as FIG. 2Q an output identifier and requestor identifier arealso sent. In step 302, the server system receives the end-user searchinformation, requestor identifier and output identifier. In step 304 theserver system retrieves from the output specifications database 117 therecords associated with the selected requester identifier-outputidentifier combination by first retrieving the mapping information fromthe requestor identifier/output table 114 in step 303. The outputspecifications includes database field information and field displayinformation which were previously entered into the output specificationsdatabase 117. In step 305 the server system uses the end-user searchinformation to retrieve the relevant records from the user inputdatabase 118. One skilled in the art would appreciate that the use ofthe end-user search information in the query of the data in the end-userinput database 118 in step 305 is separated from the use of theidentifiers in the query of the data in the output specificationsdatabase 117 in step 304 and provides a design through which the use ofthe associated identifiers is essential to the flexibility of the systempermitting, for instance, other output pages to use the same end-userdata records in the end-user input database 118 while using differentrecords in the output specifications database 117. In step 306, theserver system uses the retrieved output specifications information fromstep 304 and the user database information from step 305 to generate andsend a web page to the client system in a page description language suchas HTML for display on a browser. One skilled in the art wouldappreciated that the generated page in 306 can be generated and sent inother forms such as in an electronic mail message.

One skilled in the art would also appreciated that furtherauthentication such as password authentication can be required at step305 to limit the display of information content to authorized users. Aswell further validation such as to ensure end-user search information isvalid can be required at step 305.

For instance, following the above description, if a user wishes to viewall members who have signed-up for a golf tournament, the user submitsthis request along with the requestor identifier and the outputidentifier for this display screen to the server system in step 301using a web page such as FIG. 2Q. In step 302, the server systemreceives the end-user search information, requester identifier andoutput identifier. In step 304 the server system retrieves from theoutput specifications database 117 the records associated with theselected requestor identifier-output identifier combination by firstretrieving the mapping information from the requestor identifier/outputtable 114 in step 303. The output specifications include database fieldinformation (e.g. name, e-mail, skill level) and field displayinformation (e.g. name font color is green) which were previouslyentered into the output specifications database 117. In step 305 theserver system uses the end-user search information to retrieve therelevant records from the end-user input database 118 which containspreviously entered golf tournament sign-up information. In step 306, theserver system uses the output specifications information from step 304and the user input database information from step 305 to send a web-pagecontaining a listing of all members who have signed-up for thetournament.

FIG. 3B is a flow diagram of a routine to input user data in which arequestor identifier and an input identifier is sent to the serversystem.

Each time end-user input information is sent in step 311 from an entrypage such as FIG. 2S an input identifier and requester identifier arealso sent. In step 312, the server system receives the end-user inputinformation, requestor identifier and input identifier from the clientsystem. In step 314 the server system retrieves from the inputspecifications database 116 the records associated with the selectedrequester identifier-input identifier combination by first retrievingthe mapping information from the requestor identifier/input table 113 instep 313. The input specifications includes database field informationand may include field validation information which were previouslyentered into the input specifications database 116. In step 315 theserver system uses the retrieved input specifications information fromstep 313 and end-user input information from step 312 along with therequestor identifier and input identifier to generate and store a dataentry record in the end-user input database 118. One skilled in the artwould appreciate that the use of the identifiers permits the separationof the end-user data from the input specifications permitting, forinstance, other input pages to record the same end-user data informationin the end-user input database 118 while using different records in theinput specifications database 116. In step 316, the server system sendsa confirming web page, FIG. 2T, to the client system in a pagedescription language such as HTML for display on a browser.

One skilled in the art would appreciated that further validation such aschecking for input field length can be required at step 315 to limit theinput of information to requestor specifications if this requirement waspreviously entered into the input specifications database 116. Oneskilled in the art would also appreciated that further authenticationsuch as password authentication can be required at step 315 to limit theinput of information to authorized users.

For instance, following the above description, if a user wishes to entersign-up information into a golf tournament page, the user would entername, e-mail and skill level information in step 311 using a web pagesuch as FIG. 2S and submit the page, together with the requestoridentifier and the input identifier to the server system. In step 312,the server system receives the end-user input information, requesteridentifier and input identifier from the client system. In step 314 theserver system retrieves from the input specifications database 116 therecords associated with the requestor identifier-input identifiercombination by first retrieving the mapping information from therequestor identifier/input specifications table 113 in step 313. Theinput specifications may include database field information such aswhich database fields are used (e.g. the name, e-mail and level databasefields are used) and validation information (e.g. the name field cannotbe a null string) which were previously entered into the inputspecifications database 116. In step 315 the server system uses theretrieved input specifications information from step 313 and the userinput information from step 312 to check the validity of the user inputinformation and to generate and store a data entry record in the userinput database 118. In step 316, the server system sends a confirmingweb page, FIG. 2T, to the client system in a page description languagesuch as HTML for display on a browser.

FIG. 4A is a flow diagram of a routine to add input page specificationsin which a requestor identifier and an input identifier is sent to theserver system.

Each time information is sent in step 411 from an entry page such asFIG. 2D an input identifier and requestor identifier are also sent. Instep 414, the server system receives the requester identifier and inputidentifier along with the input specifications information. In step 415the identifier information is used to maintain the mappings between theinput specifications information and the requestor identifier-inputidentifier combination and is stored in the requestor identifier/inputidentifier table 113 along with a reference to the input specificationsinformation in the form of an assigned input record identifier. In step416, the server system creates a new input specifications record and theinput specifications information is stored in the input specificationsdatabase 116 along with the input record identifier. In step 417, theserver system sends a confirming web page such as FIG. 2E to the clientsystem in a page description language such as HTML for display on abrowser.

One skilled in the art would appreciate that the use of the input recordidentifier can be omitted if the requestor identifier and inputidentifier information is stored together with the input specificationsinformation in the input specifications database 116.

For example, if a user wishes to gather golf tournament sign-upinformation, relevant input specifications may include fields forcollecting name, e-mail and skill level. Using a web page such as FIG.2D in step 411, the user selects “text” for the field type, enters“golfer name” for the field display name and selects “required field”for validation. After the user selects Submit, the information includingthe requester identifier and input identifier is sent to the server. Instep 414, the server system receives the requestor identifier and inputidentifier along with the input specifications information. In step 415the identifier information is used to maintain the mappings between theinput specifications information and the requester identifier-inputidentifier and is stored in the requestor identifier/input identifiertable 113 along with a reference to the input specifications informationin the form of an assigned input record identifier. In step 416, theserver system creates a new input specifications record and the inputspecifications information (i.e. field type, display details andvalidation details) is stored in the input specifications database 116along with the input record identifier. In step 417, the server systemsends a confirming web page such as FIG. 2E to the client system in apage description language such as HTML for display on a browser. Theuser can repeat the above steps to enter similar information for thee-mail and skill level fields.

FIG. 4B is a flow diagram of a routine to update an input pagespecification in which a requestor identifier and an input identifier issent to the server system.

If the user chooses to update an existing input specifications recordthe user is provided with an entry page or pages such as FIG. 2F andFIG. 2G in step 441 allowing the selection of the desired inputspecifications record as identified by the input record identifier aswell as the associated input identifier. In step 442, the server systemreceives the input record identifier, input identifier and the requestoridentifier for the desired record and the server system retrieves thepreviously stored input specifications information from the inputspecifications database 116 using the mappings in the requesteridentifier/input table 113. In step 443, the server system sends anentry page such as FIG. 2H containing the retrieved input specificationsinformation corresponding to the requestor identifier, input identifierand input record identifier to the client system. After the user hasedited the entry page to his or her satisfaction the user selects Submitand sends the information, along with the requestor identifier, inputidentifier and input record identifier to the sever system. In step 444,the server system receives the requestor identifier, input identifierand input record identifier along with the updated input specificationsinformation. In step 445 the identifier information is used to retrievethe mappings between the input specifications information and therequester identifier-input identifier-input record identifer combinationfrom the requestor identifier/input identifier table 113. In step 446,the server system updates the input specifications record in the inputspecifications database 116 using the requestor identifier, inputidentifier, input record identifier and the updated input specificationsinformation. In step 447, the server system sends a confirming web pagesuch as FIG. 2I to the client system in a page description language suchas HTML for display on a browser.

FIG. 4C is a flow diagram of a routine to add an output pagespecification in which a requestor identifier and an output identifieris sent to the server system.

Each time information is sent from an output specifications page such asFIG. 2K an output identifier and requestor identifier are also sent. Instep 424, the server system receives the requester identifier and outputidentifier along with the output specifications information. In step 425the identifier information is used to maintain the mappings between theoutput specifications information and the requestor identifier-outputidentifier combination and is stored in the requester identifier/outputidentifier table 114 along with a reference to the output specificationsinformation in the form of an assigned output record identifier. In step426, the server system creates a new output specifications record andthe output specifications information is stored in the outputspecifications database 117 along with the output record identifier. Instep 427, the server system sends a confirming web page, FIG. 2T, to theclient system in a page description language such as HTML for display ona browser.

For instance, if a user wishes to output golf tournament sign-upinformation, relevant output specifications may include fields for thedisplay of name, e-mail and skill level information if they werepreviously entered in the input specifications database 116 for thatrequester identifier. Using a form such as FIG. 2K, the user enters Namein the field selection section and green in the display details section.After the user selects the submit button, the information including therequester identifier is sent to the server. In step 424, the serversystem receives the requestor identifier and output identifier alongwith the output specifications information such as the field selectionand display details. In step 425 the identifier information is used tomaintain the mappings between the output specifications information andthe requestor identifier-output identifier combination and is stored inthe requestor identifier/output identifier table 114 along with areference to the output specifications information in the form of anassigned output record identifier. In step 426, the server systemcreates a new output specifications record and the output specificationsinformation is stored in the output specifications database 117 alongwith the output record identifier. In step 427, the server system sendsa confirming web page to the client system in a page descriptionlanguage such as HTML for display on a browser. The user can thenproceeds to enter more fields to display for this screen including thee-mail and skill level.

FIG. 4D is a flow diagram of a routine to update an output pagespecification in which a requestor identifier and an output identifieris sent to the server system. If the user chooses to update an existingoutput specifications record the user is provided with an entry page orpages such as FIG. 2M and FIG. 2N in step 451 allowing the selection ofthe desired output specifications record as identified by the outputrecord identifier as well as the associated output identifier. In step452, the server system receives the output record identifier, outputidentifier and the requestor identifier and the server system retrievesthe previously stored output specifications information from the outputspecifications database 117 using the mappings in the requesteridentifier/output table 114. In step 453, the server system sends anentry page such as FIG. 2O containing the retrieved outputspecifications information corresponding to the requestor identifier,output identifier and output record identifier to the client system.After the user has edited the entry page to his or her satisfaction theuser selects Submit and sends the information, along with the requestoridentifier, output identifier and output record identifier to the serversystem. In step 454, the server system receives the requesteridentifier, output identifier and output record identifier along withthe updated output specifications information. In step 455 theidentifier information is used to retrieve the mappings between theoutput specifications information and the requestor identifier-outputidentifier-output record identifer combination from the requestoridentifier/output identifier table 114. In step 456, the server systemupdates the output specifications record in the output specificationsdatabase 117 using the requestor identifier, output identifier, outputrecord identifier and the updated output specifications information. Instep 457, the server system sends a confirming web page such as FIG. 2Pto the client system in a page description language such as HTML fordisplay on a browser.

One skilled in the art will appreciate that other mechanisms can be usedto maintain the correspondence of the output field specifications toensure that it is defined as a subset of the input field specificationswithout departing from the spirit or essential character of the presentinvention.

Although the present invention has been described in variousembodiments, it will be appreciated by those of ordinary skill in theart that the invention can be embodied in other forms without departingfrom the spirit or essential character thereof. The foregoingdescription is therefore to be considered illustrative and notrestrictive. The scope of the invention is indicated by the appendedclaims, and all changes which come within the meaning and range ofequivalents thereof are intended to be embraced therein.

What is claimed is:
 1. A method of gathering and outputting informationon a computer network where the requestor identifier is used both in theinput specifications and output specifications permitting dynamicchanges in input requirements and output characteristics comprising: arequester assignment component providing a means for generating a uniqueRequestor Identifier for each authenticated requestor and a means forstoring said Requestor Identifier in a data storage medium having aplurality of Requestor Identifiers; an input-specification assignmentcomponent providing, for each requestor identifier, a means foraccepting at least one input specification record and assigning a uniqueassociated input identifier for each record or group of records and ameans for storing said input identifier and requestor identifier in adata storage medium along with a reference to the input specificationrecord or group of records; an output-specification assignment componentproviding, for each requestor identifier, a means for accepting at leastone output specification record and assigning a unique associated outputidentifier for each output specification record or group of records anda means for storing said output identifier and requester identifier in adata storage medium along with a reference to the output specificationrecord or group of records; a user-input receiving component providing ameans for accepting input from users including requestor identifier andinput identifier and a means for using the input specification record orrecords associated with the said requester identifier and said inputidentifier in the manipulation of user data; and a user-output receivingcomponent providing a means for accepting input from users includingrequestor identifier and output identifier and a means for using theoutput specification record or records associated with the saidrequestor identifier and said output identifier in the manipulation ofuser data.
 2. The method of claim in 1 wherein the manipulation of datais verifying input data.
 3. The method of claim in 1 wherein themanipulation of data is placing data in a data storage medium.
 4. Themethod of claim in 1 wherein the manipulation of data is sending data inan electronic mail message.
 5. The method of claim in 1 wherein theinput specification record is data field information.
 6. The method ofclaim in 1 wherein the input specification record is field displayinformation.
 7. The method of claim in 1 wherein the input specificationrecord is authentication information.
 8. The method of claim in 1wherein the manipulation of data is retrieving an element of datapreviously stored using the user-input receiving component.
 9. Themethod of claim in 1 wherein the output specification record is datafield information.
 10. The method of claim in 1 wherein the manipulationof data is displaying data in a data display medium.
 11. The method ofclaim in 1 wherein the output specification record is field displayinformation.
 12. A server system for gathering and outputting datacomprising: a data storage medium storing information for a plurality ofrequestors; a data storage medium storing information for a plurality ofend-users; a requestor identifier assignment component providing areceiving component for receiving requests to generate a requestoridentifier, a requestor identifier assignment component which generatesa unique associated requestor identifier for each requestor, and arequestor identifier fulfillment component that completes the input ofthe requestor identifier information into the data storage medium; arequestor data input specification component providing a receivingcomponent for receiving requests to input requestor input informationincluding an indication of one of the plurality of requestors, an inputidentifier assignment component that generates a unique associated inputidentifier for each record or group of records associated with therequestor input information, and a requestor input fulfillment componentthat completes the input of the requestor input information togetherwith the associated requestor identifier and associated input identifierinto the data storage medium; a requestor data output specificationcomponent providing a receiving component for receiving requests toinput requestor output information including an indication of one of theplurality of requestors, an output identifier assignment component thatgenerates a unique associated output identifier for each record or groupof records associated with the requestor output information, and arequestor output fulfillment component that completes the input of therequestor output information together with the associated requestoridentifier and associated output identifier into the data storagemedium; an end-user data input component providing a receiving componentfor receiving requests to input end-user information including anindication of the requestor identifier and an indication of the inputidentifier, a data retrieval component that retrieves from the datastorage medium information for the indicated requestor identifier andthe indicated input identifier and uses the retrieved information tomanipulate the end-user data input information for the indicatedrequestor in accordance with the requestor input information, and anend-user input fulfillment component that completes the input of theend-user information into the data storage medium; and an end-user dataoutput component providing a receiving component for receiving requeststo output end-user information including an indication of the requestoridentifier and an indication of the output identifier, and a dataretrieval component that retrieves from the data storage mediuminformation for the indicated requester identifier and the indicatedoutput identifier including at least one requestor output informationand uses the retrieved information to manipulate the end-user dataoutput information for the indicated requestor.
 13. The method of claimin 12 wherein the end-user data output component further comprises: anend-user output fulfillment component that completes the output of theend-user information onto a display component.
 14. The method of claimin 12 wherein the manipulation of end-user data is retrieval.
 15. Themethod of claim in 12 wherein the manipulation of end-user data isstorage.